Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dependency date-fns-tz to v3 #44

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update dependency date-fns-tz to v3 #44

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 7, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
date-fns-tz 2.0.1 -> 3.2.0 age adoption passing confidence

Release Notes

marnusw/date-fns-tz (date-fns-tz)

v3.2.0

Compare Source

v3.1.3

Compare Source

  • [BUGFIX] Make getTimeZoneOffset's 2nd arg optional

v3.1.2

Compare Source

  • [BUGFIX] Fix formatInTimeZone use of timeZone string (#​280)

v3.1.1

Compare Source

  • [BUGFIX] getTimeZoneOffset's 2nd arg should be optional (#​281)

v3.1.0

Compare Source

  • [REFACTOR] Full rewrite in TypeScript (#​278) Thank you, @​brettwillis
  • [BREAKING CHANGE] OptionsWithTZ is now either FormatOptionsWithTZ or ToDateOptionsWithTZ, matching date-fns

v3.0.1

Compare Source

  • [BUGFIX] Fix named export typings (#​277)

v3.0.0

Compare Source

  • [UPGRADE] Support date-fns v3 (#​265) Thank you, @​christopherklint97
  • [BUGFIX] Correct import of date-fns@v3 format and use Babel Webpack loader for mjs files (#​271)
  • [BREAKING CHANGE] date-fns v2 is no longer supported
  • [BREAKING CHANGE] Renamed utcToZonedTime to toZonedTime to make the name less confusing, just search & replace
  • [BREAKING CHANGE] Renamed zonedTimeToUtc to fromZonedTime to make the name less confusing, just search & replace
  • [BREAKING CHANGE] All functions are now exported using named exports, this requires changing direct
    imports from import formatInTimeZone from 'date-fns-tz/formatInTimeZone' to
    import { formatInTimeZone } from 'date-fns-tz/formatInTimeZone'
  • [BREAKING CHANGE] Functions now don’t check the number of passed arguments, delegating this task to type checkers
    (This isn't fully implemented yet, but it should be the assumption moving forward, as it is in date-fns)
  • [BREAKING CHANGE] Arguments are not explicitly converted to the target types. Instead, they are passed as is,
    delegating this task to type checkers (This isn't fully implemented yet, but it should be the assumption
    moving forward, as it is in date-fns)
  • [BREAKING CHANGE] IE is no longer supported since date-fns no longer supports it
  • [BREAKING CHANGE] Removed flow support since date-fns also removed it

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Apr 7, 2024 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: undefined@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/date-fns
npm ERR!   date-fns@"2.29.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer date-fns@"^3.0.0" from [email protected]
npm ERR! node_modules/date-fns-tz
npm ERR!   date-fns-tz@"3.1.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-17T09_48_42_641Z-debug-0.log

@renovate renovate bot force-pushed the renovate/date-fns-tz-3.x branch 5 times, most recently from 2f61eb1 to 539e483 Compare April 17, 2024 09:48
@renovate renovate bot force-pushed the renovate/date-fns-tz-3.x branch 4 times, most recently from 2d00229 to a81ee32 Compare September 26, 2024 04:32
@renovate renovate bot force-pushed the renovate/date-fns-tz-3.x branch from a81ee32 to 08a150a Compare September 30, 2024 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants